Mobile wallet account provisioning systems and methods

ABSTRACT

A mobile device includes a display device; a processor; and a memory device configured to store instructions that, when executed by the processor, cause the processor to: present, by the display device, a user interface to a user of the mobile device for accessing a mobile online banking application; upon accessing the mobile online banking application, provide, by the display device, an option to a create a mobile wallet; responsive to receiving an indication to create the mobile wallet, provide, by the display device, a list of accounts held by the user; and receive a selection of at least one account from the list accounts to provision the at least one account to the mobile wallet for use in future mobile wallet transactions such that the at least one account from the list of accounts is auto-provisioned to the mobile wallet.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/501,880, filed Sep. 30, 2014, entitled “Mobile Wallet AccountProvisioning Systems and Methods,” which is a continuation-in-partapplication of U.S. application Ser. No. 14/266,580, filed Apr. 30,2014, entitled “Mobile Wallet Using Tokenized Card Systems and Methods,”both of which are incorporated by reference herein in their entireties.

BACKGROUND

The present disclosure relates generally to the field of systems thatuse mobile devices to transfer funds. More specifically, the presentdisclosure relates to systems and methods for enabling individuals touse their electronic devices to transfer funds, purchase products andservices.

Payments for products and services are often completed using creditcards, debit cards, checks, or cash. At the same time, most people carrysome type of mobile handheld electronic device, such as a cellularphone, smart phone, mobile handheld wireless e-mail device, personaldigital assistant, portable gaming devices, and so on. Most of thesedevices tend to have a wireless Internet connection. A person may wishto make payments to merchants or other individuals using these mobiledevices. Likewise, a person may wish to transfer funds to otherindividuals using their mobile devices. Enhanced systems and methods offacilitating such transactions would be desirable.

SUMMARY

According to one example embodiment, a computer system receives anindication from a user that the user wishes to perform a mobile wallettransaction to transfer funds to a recipient using a mobile device. Thetransaction is authenticated by the computer system. The authenticationincludes receiving login credentials manually entered by the user anddetermining that the login credentials match stored login credentialsfor the user. The authentication further includes determining that themobile device has a device token stored thereon that matches a devicetoken stored in a database of the computer system. The device tokenuniquely identifies the mobile device in the computer system. Theauthentication further includes determining that the mobile device has acustomer token stored thereon that matches the customer token stored inthe database. The customer token uniquely identifying the customer inthe computer system. The computer system transmits the funds to therecipient responsive to the authenticating step.

According to another example embodiment, a financial institutioncomputer system creates a new financial account for a user. Thefinancial institution computer system activates the new account as asource of funds for a mobile wallet. The user does not need to take anyaction outside of the mobile wallet to have the account activated as asource of funds for the mobile wallet.

According to another example embodiment, a computer system receives anindication from a user that the user wishes to create a mobile wallet.The computer system accesses a database to retrieve a list of one ormore accounts held by the user at a financial institution. The computersystem generates a screen display to present to the user via a mobiledevice, the screen display showing the list of accounts held by theuser. The computer system receives a user selection of at least one ofthe accounts. In response to the user selection, the at least oneaccount is provisioned to the mobile wallet.

According to another example embodiment, a financial institutioncomputer system receives online banking login credentials from a mobiledevice at an online banking website of a financial institution toinitiate a mobile online banking session for a user. During the onlinebanking session, the computer system presents the user with a link tohave a mobile wallet circuit placed on the mobile device. The computersystem places the mobile wallet circuit on the mobile device responsiveto a user selection of the link, including transmitting a mobile walletapplication to the mobile device and causing installation of the mobilewallet application to occur on the mobile device.

BRIEF DESCRIPTION OF THE FIGURES

The details of one or more implementations are set forth in theaccompanying drawings and the description below. Other features,aspects, and advantages of the disclosure will become apparent from thedescription, the drawings, and the claims, in which:

FIG. 1 is a block diagram of a computer-implemented payment processingsystem, according to an example embodiment.

FIG. 2 illustrates a payment process that may be implemented by thesystem in FIG. 1 according to an example embodiment.

FIG. 3 illustrates a user registration process and a token generationprocess during registration, according to an example embodiment.

FIGS. 3A-3F illustrate display screens that may be displayed to the userduring the process of FIG. 3 .

FIG. 4 illustrates a payment code generation process for anauthenticated mobile wallet session, according to an example embodiment.

FIGS. 4A-4D illustrate display screens that may be displayed to the userduring the process of FIG. 4 .

FIG. 5 illustrates a Track 1 format for a generated QR code that may becreated in the token generation process, according to an exampleembodiment.

FIG. 6 illustrates a Track 2 format for a generated QR code that may becreated in the token generation process, according to an exampleembodiment.

FIG. 7 illustrates a tokenized primary account number (TPAN) formatwithin the QR code of FIGS. 5-6 , according to an example embodiment.

FIG. 8 illustrates a Track 2 format for a code generated, according toan example embodiment.

FIG. 9 illustrates a process that may be implemented by the system inFIG. 1 according to an example embodiment.

FIG. 10 illustrates a payment process that may be implemented by thesystem in FIG. 1 according to an example embodiment.

DETAILED DESCRIPTION

Before turning to the figures which illustrate example embodiments, itshould be understood that the application is not limited to the detailsor methodology set forth in the following description or illustrated inthe figures. It should also be understood that the phraseology andterminology employed herein is for the purpose of description only andshould not be regarded as limiting.

Referring generally to the figures, systems and methods for providingtoken generation and validation features for a payment processing systemare described. More particularly, the present disclosure relates to theuse of codes with tokens for validation during payment processing. Thecodes may be transmitted, e.g., using optical image methods (e.g., QRcode), NFC, wireless, Bluetooth, low energy Bluetooth, RFID, hypersonic,Wi-Fi, cellular 3G, 4G, GSM, LiFi, etc. The systems and methodsdescribed herein may be implemented for users having a mobile walletimplemented on a mobile device. The mobile wallet allows the user accessto accounts via the mobile device to provide payments to merchants orother users. The systems and methods described herein allow forintegration between a mobile wallet server and a merchant for processinga payment.

In an embodiment of the present disclosure, a code representing asubstitute card number may be generated and formatted for use as part ofa validation system. When a user registers for a mobile wallet account,a customer token may be generated for the user and a device token may begenerated for the device used by the user. The customer token and devicetoken may be used to verify further transactions between the user andthe mobile banking system or mobile wallet account.

When the user logs into his or her mobile wallet and wishes to make apayment using funds in the user's accounts, the customer token anddevice token are sent or provided to a server system. A substitute cardnumber (tokenized) including a trace ID number as described below may beprovided to the user by a mobile wallet computer system. The mobilewallet computer system and a point of sale (POS) device, e.g., at thestore location at which the payment is to be submitted, use thesubstitute credit card number to authenticate the transaction. Thesubstitute card number may be formatted to include a portion of anactual card number held by the user, e.g., so that the last four digitsappearing on a receipt provided to the user match those of the user'sactual card number, even though a substitute card number was provided tothe merchant to process the payment.

In various embodiments, the substitute card number (tokenized) includinga trace ID number as described below may be converted back into theactual credit card number by a mobile wallet computer system. Forexample, the merchant point of sale device may provide the substitutecard number to an acquirer processor computer system, which in turn mayprovide the substitute card number to the mobile wallet computer system.In response, and after authenticating the transaction, the mobile walletcomputer system may return the actual card number to the acquirerprocessor computer system. The acquirer processor may then provide theactual card number to a payment network, which in turn may provide thecard number to a source account (credit card issuer) computer system forpayment processing.

In other embodiments, rather than providing the substitute card numberto the mobile wallet computer system, the acquirer processor computersystem may provide the substitute card number to a payment networkcomputer system. In turn, the payment network computer system mayprovide the substitute card number to the mobile wallet computer system,which, after authenticating the transaction, may then return the actualcard number to the payment network computer system. The payment networkcomputer system may then provide the actual card number to a sourceaccount computer system for payment processing.

Referring to FIG. 1 , a computer-implemented payment processing system100 is shown, according to an example embodiment. The payment processingsystem 100 may be used to set up and utilize a mobile wallet. The usermay be a business entity and/or an individual consumer that has one ormore source accounts with a financial institution. The source accountsmay include business or consumer demand deposit, credit card, debit cardaccounts, lines of credit, and so on. The mobile wallet account may becreated for the user to transmit funds from a source account to pay forgoods or services to a merchant. Additionally, funds can be transferredfrom the source account to another person.

The payment processing system 100 may include, among other systems, amobile device 110, a mobile wallet bank computer system 120, a sourceaccount bank computer system 130, a merchant computer system 140, anacquirer/processor computer system 145 and a payment system 150. Thevarious systems may communicate through a network 160, which may includeone or more of the Internet, cellular network, Wi-Fi, Wi-Max, aproprietary banking network, or any other type of wired or wirelessnetwork. In some embodiments, the mobile wallet bank computer system 120and source account bank computer system 130 may be owned by the sameentity. In other embodiments, the mobile wallet bank computer system 120and source account bank computer system 130 may be owned by a differententity.

The mobile wallet bank computer system 120, the source account bankcomputer system 130, the acquirer/processor computer system 145 and thepayment system 150 may each include a computer system (e.g., one or moreservers each with one or more processing circuits), each including aprocessor and memory. The processors may be implemented as applicationspecific integrated circuits (ASICs), one or more field programmablegate arrays (FPGAs), a group of processing components, or other suitableelectronic processing components. The memory may be one or more devices(e.g., RAM, ROM, Flash memory, hard disk storage, etc.) for storing dataand/or computer code for completing and/or facilitating the variousprocesses described herein. The memory may be or include non-transientvolatile memory, non-volatile memory, non-transitory computer storagemedia. The memory may include data base components, object codecomponents, script components, or any other type of informationstructure for supporting the various activities and informationstructures described herein. The memory may be communicably connected tothe processor and include computer code or instructions for executingone or more processes described herein.

The mobile wallet account may be established in a variety of ways, forexample, through an online banking area of a website of the bankinginstitution that operates the mobile wallet bank computer system 120.

The mobile device 110 may be used by an individual user (e.g., abusiness owner or employee, a consumer, etc.) to create and interactwith a mobile wallet account. The mobile device 110 may, for example be,a cellular phone, smart phone, mobile handheld wireless e-mail device,personal digital assistant, portable gaming device, or other suitabledevice. The mobile device 110 includes a network interface logic 112, adisplay device 114, an input device 115, and a mobile wallet clientapplication 116. The network interface logic 112 may include, forexample, program logic that connects the mobile device 110 to thenetwork 160. For example, the mobile device 110 may receive and displayscreens including account information, transaction instructions, and soon. In one embodiment, a screen may be used to request a username andpassword information from the user, to prompt the user to provideinformation regarding the amount of a payment and which merchant orindividual (e.g., name, address, phone number or e-mail, a selection ofa recipient by the user from his/her memory or from the mobile device110, etc.) is to receive the payment. Such screens are presented to theuser via the display device 114. The input device 115 may be used topermit the user to initiate account access and to facilitate receivingrequested information from the user. The input device 115 may include,for example, a keypad or keyboard, a touchscreen, a microphone, or anyother device that allows the user to access the payment processingsystem 100. As will be appreciated, in addition to or instead of themobile device 110, users may also be provided with the ability to accessthe payment processing system 100 using another type of computer (e.g.,a desktop or laptop computer executing browser software) to perform theoperations described herein as being performed by the mobile device 110.

The mobile wallet client application 116 or mobile wallet circuit mayinclude program logic executable by mobile device 110 to implement atleast some of the functions described herein. In order to make themobile wallet circuit 116, the mobile wallet bank computer system 120may provide a software application and make the software applicationavailable to be placed on the mobile device 110. For example, the mobilewallet bank computer system 120 may make the software applicationavailable to be downloaded (e.g., via the online banking website of themobile wallet bank, via an app store, or in another manner). Responsiveto a user selection of an appropriate link, the mobile walletapplication may be transmitted to the mobile device and may cause itselfto be installed on the mobile device 110. Installation of the softwareapplication creates the mobile wallet circuit on the mobile device 110.Specifically, after installation, the thus-modified mobile device 110includes the mobile wallet circuit (embodied as a processor andinstructions stored in non-transitory memory that are executed by theprocessor).

As will be appreciated, the level of functionality that resides on themobile device 110 as opposed to the mobile wallet bank computer system120 may vary depending on the implementation. The client application 116may provide an interface that is configured to receive and displaymobile web pages received from the mobile wallet bank computer system120 (e.g., web pages prompting the user to provide information to createan account, web pages displaying account balance information and pasttransactions, and so on). Upon initiation of a transaction, the clientapplication 116 may request data from the mobile wallet computer system120 to generate a unique code/token. The unique code/token may then betransmitted by the mobile device 110 to the merchant computer system 140as part of a transaction to facilitate authentication of thetransaction. In other embodiments, the mobile wallet bank computersystem 120 may implement the code/token generator.

The mobile wallet client application 116 is used in connection withmerchant computer system 140 located at a brick and mortar storelocation. Additionally, the mobile wallet application 116 may also beused in connection with online merchant transactions. In anotherembodiment, merchants may be provided with the ability to have a mobilestorefront and profile within the mobile wallet client application 116.For example, merchants may be provided with the ability to displaymarketing material, provide information, and promote products ordiscounts. Merchants may also be provided with the ability to sell itemsdirectly through their mobile storefront for the account holder topurchase from within the mobile wallet client application 116.

The mobile wallet client application 116 may offer a user to choose anyone of the accounts for transferring funds to the merchant for goods orservices. An account holder may select a default account that is used tomake payments. The account holder may use account selection logic toselect the account the account holder wants to use to pay the merchantor other recipient.

The mobile wallet bank computer system 120 includes code/token generator118, account processing logic 122, an accounts database 124, networkinterface logic 126, transaction verification logic 127, and an accountdirectory 128. In one embodiment, the mobile wallet bank computer system120 is operated by a first banking entity that maintains and handlestransaction processing for mobile wallet accounts. The mobile walletaccounts may be created via interaction of the mobile wallet application116 with the mobile wallet bank computer system 120. The user may or maynot have conventional bank accounts with the banking entity thatmaintains the mobile wallet bank computer system 120. If the user doesnot have bank accounts with the entity that maintains the mobile walletbank computer system 120, then accounts associated with another bankingentity may also be used. Again, in such an embodiment, the flow of fundsinto and out of the mobile wallet accounts may also be processed by thefirst banking entity using the mobile wallet bank computer system 120.

The mobile wallet bank computer system 120 is configured to storeinformation regarding mobile wallet accounts. By way of example,information for a specific mobile wallet account 125 is shown as beingstored in the accounts database 124. As will be appreciated, theaccounts database 124 may also store information regarding many othermobile wallet accounts (not shown). As will also be appreciated, theextent to which transaction details are tracked and maintained inaccount processing logic 122 and stored in a storage database providedby the mobile wallet bank computer system 120 may vary in differingembodiments. The account database 124 may store details regarding creditcard accounts. In particular, the account database 124 may store eachfinancial transaction that occurred. Each financial transaction mayinclude the amount of the transaction and the merchant.

The code generator 118 may receive a request from an account holder toinitiate a transaction. In response, the code generator 118 may generatea code that may be transmitted by the mobile device 110 to the merchantcomputer system 140. As will be appreciated, any suitable method may beused to transmit the code. In various embodiments, the code may betransmitted using optical image methods (e.g., QR code), NFC, wireless,Bluetooth, low energy Bluetooth, RFID, hypersonic, Wi-Fi, cellular 3G,4G, GSM, LiFi, etc. For purposes of providing an example, it issometimes assumed in the discussion of FIGS. 1-11 that an optical methodis used (e.g., QR code). In various embodiments, the code may begenerated without the account holder providing the merchant's name oramount of transaction. The code generator 118 can be configured togenerate a code that incorporates at least one of a date, time, traceID, unique transaction identifier, and geographic location of the mobiledevice. In other embodiments, the code generator 118 may generate atokenized numerical code that is in the Track 1 and Track 2 formats asspecified by the ISO 8583 specification.

The code may incorporate at least a portion of an account number for asource account that is associated with the mobile wallet account. Theincorporated user account number indicates the payment method to beassociated with the transaction (e.g., which of the user's credit cardswill be used for the transaction). The code may be generated such that acombination of random digits and a portion of a payment card number areincluded in the code, e.g., so that the last four digits appearing on areceipt provided to the user match those of the user's actual cardnumber, even though a substitute card number was provided to themerchant. The various fields of such a code, and the format of such acode, are described in greater detail in FIGS. 5-8 .

The mobile wallet account 125 holds funds that are transmitted to arecipient 140 upon receiving instructions from the user through themobile device 110. As described below, funds flow into and out of themobile wallet account 125 through the payment system 150. The mobilewallet account logic 120 is connected to the payment system 150 throughthe network 160. The network interface logic 126 may include, forexample, program logic that connects the mobile wallet bank computersystem 120 to the network 160.

The mobile wallet bank computer system 120 further includes transactionverification logic 127. The transaction verification logic 127 mayreceive a transaction amount from the merchant computer system 140. Insome embodiments, the transaction verification logic 127 may generate amessage to send to the mobile device 110 for verifying the transactionamount. Upon receiving the verification message, the account holder viathe mobile device 110 may approve or deny the transaction amount for themobile wallet bank computer system 120.

The source account computer system 130 includes account processing logic132, an accounts database 134, and network interface logic 136. In anexample embodiment, as previously indicated, during registration processfor the mobile wallet account 125, the user may be prompted to identifya source account 135, that is, a source of funds for the mobile walletaccount. The source account 135 may be an existing demand depositaccount or a credit card account held by the user with the samefinancial institution or another financial institution. When the mobilewallet account 125 is created, the user is prompted to provide bankaccount information (e.g., routing number and/or account number) for thesource account 135 that is used as a source of funds for the mobilewallet account 125. Thus, the financial institution that provides themobile wallet account 125 for the user and the financial institutionthat typically provides banking services to the user may be twodifferent financial institutions. In such situations, a second bankingentity that maintains and handles transaction processing for sourceaccounts may operate the source account computer system 130. In othersituations, the computer systems 120 and 130 may be considered as beingintegrated in a single payment processing system (e.g., if the twofinancial institutions are the same). As will be appreciated, in asituation where the mobile wallet computing system 120 has many users,some users may have all their mobile wallet source accounts at the samebank that operates the mobile wallet computer system 120, some users mayhave all their mobile wallet source accounts at a bank other than thesame bank that operates the mobile wallet computer system 120, and someusers may have some of their mobile wallet source accounts at the samebank that operates the mobile wallet computer system 120 and other oftheir mobile wallet source accounts at a bank other than the bank thatoperates the mobile wallet computer system 120.

The merchant computer system 140 may be used at a point of sale locationto conduct transactions with the account holder. For example, themerchant computer system 140 may include a point of sale computer systemsuch as a cash register system connected to a central server systemoperated by the merchant. As another example, the merchant computersystem 140 may include a mobile computing device (e.g., smart phone,tablet PC, etc.) operated by a store clerk as the clerk moves throughoutthe store. Again, the mobile computing device in such an embodiment mayconnect to a central server system operated by the merchant.

The merchant computer system 140 includes network interface logic 142, acode scanner 144, location indicator logic 146, fund requesting logic148, and fund receiving logic 149. In one embodiment, the networkinterface logic 142 is configured to allow the merchant computer system140 to communicate with the network 140. The network interface logic 142sends and receives data from the mobile device 110 and the mobile walletbank computer system 120.

The code scanner 144 may be configured to scan codes, such as but notlimited to, optically scanned or non-optically scanned codes. In theembodiment of the present disclosure, the code scanner 204 scans one ormore types of codes. After receiving the code, the scanner 144determines the information that was incorporated into the code by themobile device 110 or the mobile wallet bank computer system 120 thatgenerated the code, as described below.

The location indicator logic 146 provides an indication of thegeographic location of the code scanner 144. In one embodiment, thelocation indicator logic 146 may be programmed with the known address ofthe merchant location as the location of the code scanner, such that thelocation of the merchant can be compared with the location of the mobiledevice 110 as part of authenticating a transaction.

The fund requesting logic 148 communicates a fund request via thenetwork interface logic 142 to the acquirer/processor computer system145. In some embodiments, the fund requesting logic 148 may send thetokenized card number (that includes an issuer identification number (TN), trace ID (generated numbers), checksum helper digit, last 4 digitsof the actual card number) received from the user to theacquirer/processor computer system 145. In response to receiving atokenized card number, the acquirer processor computer system 145 sendsthe tokenized card number to the mobile wallet bank computer system 120,which in turn sends the actual card number and a trace ID (embeddedwithin the issuer discretionary field) to the acquirer processorcomputer system 145. The fund receiving logic 149 determines whenpayment has been received by the merchant computer system 140 andallocates the payment accordingly.

The merchant computer system 140 may further connect to or integratewith other hardware. For example, in one embodiment, the merchantcomputer system 140 may connect to a card reader for reading creditcards, debit cards, stored value cards, and so on. As another example,the merchant computer system 140 may be configured to prompt the user toprovide a random security code. The random security code may begenerated by the mobile device 110, by a separate security dongle, or inanother manner. The security code may be provided to the merchantcomputer system 140 directly by the mobile device, may be keyed into themerchant computer system 140 (e.g., by a store clerk), or may bereceived in another manner.

The acquirer processor computer system 145 includes a computer systemthat transmits and receives messages from the mobile wallet bankcomputer system 120, the merchant computer system 140, or the paymentsystem 150. In various embodiments, the acquirer processor computersystem 145 may receive the tokenized card information and route thereceived information to the mobile wallet bank computer system 120. Inother embodiments, the acquirer processor computer system 145 mayreceive the actual card information from the mobile wallet bank computersystem 120 with the trace ID embedded within the issuer discretionaryfield in track 2 format. In some embodiments, the acquirer processorcomputer system 145 may transmit the actual card information with thetrace ID to the payment system 150. In various embodiments, the acquirerprocessor computer system 145 may process the payment in the mobilewallet system described herein.

In other embodiments, and as previously noted, the acquirer processorcomputer system 145 may instead route the tokenized card informationwith the trace ID number to payment system 150. In turn, the paymentsystem 150 may provide the substitute card number to the mobile walletcomputer system 120, which, after authenticating the transaction, maythen return the actual card number to the payment system 150. Thepayment system 150 may then provide the actual card number to a sourceaccount computer system 130 for payment processing.

The payment system 150 may comprise at least one card network 152. Insome embodiments, the payment system comprises multiple card networks152, such as Visa®, MasterCard®, American Express®, Discover®, DinersClub®, etc. In such an embodiment, the appropriate card network 152 maybe determined based on the first digit of the actual account number(i.e., “4” corresponding to Visa®, “5” corresponding to Mastercard®, “6”corresponding to Discover®, and so on). The acquirer processor computersystem 145 may therefore route the transaction to the appropriate cardnetwork 152 based on the first digit of the substitute credit cardnumber. The card network 152 may then route the substitute card numberto the mobile wallet computer system 145 based on the issueridentification number (IIN). For example, the card network 152 mayidentify the credit card number provided by the acquirer processorcomputer system 145 as being a substitute credit card number and not anactual credit card number based on the TIN. In one embodiment, thisidentification occurs based on the TIN being a card network-owned TINthat has been licensed to the mobile wallet bank and that has beendesignated by the mobile wallet bank and the card network for use inmobile wallet transactions. In such an arrangement, the acquirerprocessor computer system 145 processes the transaction like any othercredit card transaction, and it is not necessary for the acquirerprocessor computer system 145 to be aware that the transaction is amobile wallet transaction. Given the relatively limited number of cardnetworks (e.g., Visa®, MasterCard®, American Express®, Discover®, DinersClub®, etc.), and given the much larger number of acquirer/processors,such an arrangement has the technical benefit of reducing modificationsto existing computer systems to implement the features described herein.In other embodiments, this identification is made based on an indicationfrom the merchant computer system 140 and/or the acquirer processorcomputer system 145 that the transaction is a mobile wallet transaction.Based on the TIN, the card network 152 may transmit the substitute cardnumber to the mobile wallet computer system in turn receive the actualcard number, expiration date, and authentication code (e.g., cvv, etc.)from the mobile wallet bank computer system 120.

The payment processing system 100 may further include additional bankcomputer systems that may allow the mobile wallet platform of thepresent disclosure to be accessed by consumers and merchants that bankat various different banking institutions. The additional bank computersystems may provide the services described herein through multiplebanks, allowing for broader adoption of the mobile wallet platform.

FIG. 2 illustrates a process 200 that may be implemented by the systemin FIG. 1 . When a user wishes to make a payment at a merchant, forexample, the user may access the mobile wallet client application 116 byentering a PIN or other login credentials and then selecting a “pay now”or similar button. For example, the user may be located at a merchantlocation and may wish to pay for a good or service. As another example,the user may be located away from the merchant location or be engaged inan online transaction.

At step 201, the mobile device 110 requests access to funds in themobile wallet via the mobile wallet bank computer system 120 to pay fora good or service. The mobile device 110 may provide a PIN, a customerID, and a device ID to the mobile wallet bank computer system 120. Theuser may be identified and authenticated based on a match of these threedata elements with information stored in the mobile wallet bank computersystem 120. Further, the user's mobile wallet account information may belocated/determined.

Next, at step 202, the mobile wallet bank computer system 120 maygenerate a tokenized credit card number as described in greater detailbelow. The tokenized credit card number may include a few generatednumbers and a few numbers from the actual credit card number. In oneembodiment, the tokenized credit number starts with an issueridentification number (IIN) that corresponds to the mobile wallet bankcomputer system 120, ends with the last four digits of the actual creditcard account number of the credit card that is being used in thetransaction, and further includes intervening digits including a traceID and a checksum helper digit. The trace ID is described in furtherdetail below and allows for enhanced authentication during the paymentprocess. The may permit checksum verification of the tokenized creditcard number. Various checksum algorithms may be used to verify that thetokenized credit card number is a valid credit card number.

The tokenized credit card number may be transmitted to the mobile device110 in the form of a code. For example, the data may be encoded inaccordance with the track 1 and/or track 2 formats used in the magneticstripes of credit cards. In some embodiments, the code is formatted inTrack 2 format. In either case, the primary account number field maycontain the tokenized credit card number and the issuer discretionaryfield may contain the payment token. In yet other embodiments, anotherformat is used.

At step 203, the tokenized credit card number is transmitted to themobile device 110. If the mobile wallet bank computer system 120 and thesource account computer system 130 are different computer systems (e.g.,if the user is using a credit card that is provided by a different bankthan the bank the operates the mobile wallet computer system 120), thenthe trace ID may also be sent to the source account computer system 130at step 203.

At step 205, the mobile device 110 may display or otherwise transmit thetokenized credit card number to merchant computer system 140 (e.g.,using a QR code, NFC, wireless, Bluetooth, low energy Bluetooth, RFID,hypersonic, Wi-Fi, cellular 3G, 4G, GSM, LiFi, or other method). At step207, after receiving the tokenized card number, the merchant computersystem 140 sends the transaction to an acquirer processor computersystem 145 for processing.

Next, at step 209, the acquirer processor computer system 145 sends thetokenized card number to the mobile wallet bank computer system 120.After receiving the request from the acquirer processor computer system145, the mobile wallet bank computer system 120 may determine the actualcard number and send the actual card number back to the acquirerprocessor at step 211. In one embodiment, the determination of theactual card number may occur by searching for the account informationassociated with the payment token and/or trace ID within the tokenizedcard number. Additionally, the trace ID from the tokenized card numbermay be sent with the actual card number at step 211. At this point, theissuer discretionary field is no longer need for the payment token,hence, the trace ID may be sent to the acquirer processor computersystem 145 in the issuer discretionary field.

At step 212, the acquirer processor computer system 145 sends the actualcard number and the trace ID to the payment system 150 for processing apayment. The payment system 150 sends the actual card number with thetrace ID and the transaction amount to the source account bank computersystem 130 at step 213. The source account bank computer 130 mayretrieve the trace ID that was received from the mobile wallet bankcomputer system 120 by searching for the actual card number that wasreceived from the payment system 150. The source account bank computer130 may compare the trace ID that was received/stored at step 203 withthe trace ID that was received from the payment system 150 at step 213.Assuming there is a match, the source account bank computer 130 mayissue an approval for the transaction. After verifying the actual cardnumber and the trace ID in the issuer discretionary field, the sourceaccount bank computer system 130 may send an approval to the paymentsystem 150 at step 215. The approval message may be sent from thepayment system 150, to acquirer processor computer system 145, to thepoint of sale system 140, in steps 217 and 219. Upon receiving theapproval message the point of sale system 140 may generate a receipt forthe user. In some embodiments, the receipt may be sent to the mobiledevice 110 electronically. In other embodiments, the receipt may beprinted physically at the point of sale location. The receipt mayinclude the last four digits of the actual credit card account number ofthe credit card that was used in the transaction.

The use of the payment token and trace ID as described herein allows fortwo levels of authentication. The payment token is generated by themobile wallet computer system at step 202. The payment token is thentransmitted to the mobile device 110, then to the merchant computersystem 140, then to the acquirer processor computer system 145, andeventually back to the mobile wallet computer system 120 where it ismatched with the original payment token generated at step 202.Similarly, the Trace ID is also generated by the mobile wallet computersystem at step 202, and then transmitted to the mobile device 110, thento the merchant computer system 140, then to the acquirer processorcomputer system 145, and eventually back to the mobile wallet computersystem 120 where it is matched with the Trace ID generated at step 202.In the case of the Trace ID, however, the Trace ID is then furthertransmitted back to the acquirer processor computer system 145, then tothe payment system 150, and then to the source account computer system130 where it is matched with the Trace ID generated at step 202.Accordingly, the trace ID used in conjunction with the tokenized creditcard number allows both the mobile wallet bank computer system 140 andthe source account bank computer system 130 to authenticate thetransaction. Using the trace ID in the above described manner may permitthe source account bank computer system 130 and the mobile wallet bankcomputer system 120 to verify the trace ID at least twice prior toapproving a transaction and transferring funds. Further, and asdescribed in greater detail below, the trace ID may be used by thesource account computer system 130 to determine whether the credit cardtransaction was a mobile wallet transaction (e.g., as opposed to anin-person card-present transaction involving use of the user's physicalcredit card, as opposed to an online transaction, and so on). Hence, thesource account bank computer system 130 may provide a different customerexperience to the mobile wallet user. The source account bank computersystem 130 may also determine risk differently for transactions that usea mobile wallet.

In some embodiments, instead of embedding the trace ID in a tokenizedcredit card account number at step 202, the actual credit card number istransmitted to the mobile device 110 and the merchant computer system140. In such an embodiment, the trace ID may be included in the issuerdiscretionary field at step 202, and the payment token may becommunicated in another manner or another payment matching mechanism maybe used. The trace ID may be stored in the issuer discretionary fieldand may travel though the payment processing system, until it isverified by the source account bank computer system 130. After beingverified by the source account bank computer system 130, the transactionmay be approved and the funds may be transferred from the source accountbank computer system to the acquirer processor computer system 145. Inother embodiments, the same financial institution may own the sourceaccount bank computer system 130 and the mobile wallet bank computersystem 120.

Referring now to FIG. 3 and FIGS. 3A-3F, FIG. 3 is a flow chart of aprocess 300 detailing a user registration process and a token generationprocess during registration, according to an example embodiment. FIGS.3A-3F are screens that may be displayed to the user during the process300 of FIG. 3 according to an example embodiment. Process 300 may beexecuted by a mobile device 110 and a mobile wallet bank computer system120 that is configured to create and manage a mobile wallet account.Process 300 may be executed for a user who wishes to start a mobilewallet account 125 for a source account 135. In the example of FIG. 3 ,it is assumed that the user has an account at the bank that operates themobile wallet computer system 140. As will be appreciated, a similarprocess may be used for users that have accounts only at other banks.

As previously indicated in connection with FIG. 1 , a user may performthe registration via an online banking website of the mobile walletbank. For example, as shown in FIG. 3A, a user may select a button 301for an online banking application on the mobile device 110.

After the button 301 is selected, the user may be presented with ascreen as shown in FIG. 3B. Process 300 includes receiving userauthentication information into the mobile wallet bank computer system120 using existing financial institution credentials (step 302).Existing credentials may include, for example, a username and passwordcombination or card information (card number, account number, expirationdate, CVV) for an online banking website of the bank that operates themobile wallet computer system 120. For example, in FIG. 3B, thecredentials are entered in fields 303 and 305, respectively, of a loginscreen to the online banking website. In one embodiment, the credentialsmay match keyboard-entered credentials that are used to access thesource account via online banking. In other embodiments, the credentialsmay match other types of authentication credentials that are used toaccess online banking (e.g., facial recognition on a captured image orvideo of the user on a camera of the mobile device, voice or speechrecognition captured by an input device of the mobile device,fingerprint authentication, etc.). After providing online banking logincredentials as shown in FIG. 3B, the user may be taken to a top-levelonline banking screen as shown in FIG. 3C. The screen shown in FIG. 3Cshows an overview of accounts and account balances held by the user.

Process 300 further includes initiating a registration process for amobile wallet account with the user (step 304). Step 304 includesreceiving a user indication to create a new mobile wallet account. Insome embodiments, the user may be presented with a menu option on his orher mobile device to create a new mobile wallet account, among otheroptions. For example, in the top-level screen shown in FIG. 3C, a button327 is provided that allows the user to receive additional informationabout the mobile wallet application. After selecting the button 327 inFIG. 3C, the user may be taken to a mobile wallet introductory screen asshown in FIG. 3D. In the screen shown in FIG. 3D, the user is providedwith an option to tour the mobile wallet application and with an optionto initiate the mobile wallet registration. Upon selecting button 329,the mobile wallet registration process is initiated. After selecting thebutton 329 in FIG. 3D, the user may be taken to a first screen for themobile wallet registration as shown in FIG. 3E.

Process 300 further includes receiving user account information (step306). Receiving the user account information may include prompting theuser to provide mobile wallet login credentials, e.g., a PIN numberassociated with a debit card or credit card held by the user at thebank. For example, in FIG. 3E, the user enters a PIN number in field331. The user may also be prompted to identify the source account(s) theuser wishes to associate with the mobile wallet account. For example,the user may enter information about accounts held at other banks thatmay serve as source accounts. In other embodiments, the user may bepresented with various fields on the mobile device that allow the userto select one or more source accounts held by the user, to enter accountinformation (e.g., an account number) in one or more fields, orotherwise. For example, as shown in FIG. 3F, the user may be presentedwith a list 333 of accounts the user has with a particular sourceaccount bank computer system, and may choose one or more accounts toview account information and to select the account for use with themobile wallet account. Thus, the mobile wallet may auto-provision theexisting accounts of the user to the mobile wallet, without the userhaving to manually enter the 16-digit credit card account number orother account information (e.g., in the case of other types of financialaccounts). The user may further provide information to create a userprofile including other information as warranted. In some embodiments,the mobile wallet computer system 120 may establish a connection withthe computer systems 130 of other financial institutions, such that theaccounts held by the user at the other financial institutions may beauto-provisioned to the mobile wallet as well. In both cases, the usermay be provided with information about current account balancesregarding the accounts.

Process 300 further includes generating a customer token and devicetoken (step 308), and sending the customer token and device token to themobile device of the user (step 310). The customer token and devicetoken may be tokens that identify the user and the associated mobiledevice to the mobile wallet bank computer system in the future. Thetokens are encrypted by the mobile wallet bank computer system andprovided to the mobile device. The mobile device stores the tokens forfuture use. In one example embodiment, each time the user accesses themobile wallet system with a new mobile device 110, the mobile device isassigned its own device token. A device and customer token are stored oneach device in order to bind the device to the user (one device can onlyhave one wallet user, but one user can have multiple devices). Once amobile device for mobile wallet account is registered, the user onlyneeds to enter their existing PIN to access their mobile wallet from theregistered device (which PIN may be typically eight characters or lessand consist only of numbers). The full login credentials associated withonline banking are not needed (which often consist of a combination oflower case letters, upper case letters, numbers, and special characters(e.g., punctuation marks)). Instead, possession by the user of theregistered device provides an additional level of authentication thatavoids the need for full login credentials. Additionally, it may benoted that the level of functionality available the user through themobile wallet may be less than the level of functionality available tothe user through the full online banking website, thereby providingfurther risk mitigation.

Process 300 further includes receiving a default payment method from theuser (step 312) and completing the registration (step 314). Step 314 mayinclude a user accepting terms and conditions associated with use of themobile wallet account. The default payment method may indicate how auser wishes to normally pay for a particular transaction. For example,the user may provide options relating to how to manage overdrafts,whether the total payment should be provided in one or more payments, orotherwise. Process 300 may include storing the default payment method(step 316) in the profile database of the mobile wallet bank computersystem 120 (or another database of the mobile wallet bank computersystem). The default payment method may be recalled by the mobile walletbank computer system 120 during a future payment process.

Process 300 may also include generating and sending an offline codetoken to the source account bank computer system. The offline code maybe used by the payment processing system, and more particularly thesource account bank computer system, to execute a payment for the userwhen the mobile device is offline, or for other account managementpurposes. In some embodiments, the mobile device may store one or moreoffline codes to provide to the merchant. The mobile device 110 may notcontact the mobile wallet bank computer system 120 and may provide thecode to the merchant computer system 140.

As will be appreciated, the arrangement of FIG. 3 facilitates keepingthe list of source accounts that is up to date and accurate to the user.For example, each time a transaction is to be performed, the mobilewallet computer system 120 may access a list of accounts held by theuser at the mobile wallet bank. In some cases, an account that waspreviously active may no longer be active. For example, a user may havereported a physical credit card associated with a credit card account ashaving been lost or stolen. Prior to presenting a list of availablesource accounts to the user in the context of a particular transaction,the mobile wallet computer system 120 may determine that apreviously-provisioned source account is no longer available as a sourceof funds. Hence, when the mobile wallet computer system 120 generates ascreen display to present to the user via a mobile device showing thelist of accounts held by the user at the financial institution, thepreviously-provisioned source account that is no longer available as asource of funds may be excluded from the list. When the list ofavailable source accounts is presented to the user, the user may selecta new source account for the transaction. For example, if the creditcard account was the user's default payment method, the user may selecta new default payment method (e.g., an existing demand deposit account).

Additionally, the arrangement may also permit new accounts to beactivated and added to the mobile wallet, e.g., a new card account, anew savings account, a new line of credit, and so on. In the case of anew card account, the new card account may, for example, be a new creditcard account, a new demand deposit account with a debit card, or anexisting demand deposit account with a new debit card.

For example, in the case of a lost or stolen credit card, the bank maycreate a new credit card account in replacement of the credit cardaccount for which the physical credit card was reported as having beenlost or stolen. When the mobile wallet computer system 120 accesses thelist of accounts held by the user, the mobile wallet computer system 120may identify the new credit card account as being an account that hasnot yet been provisioned to the mobile wallet. When the screen displayis generated showing the list of accounts held by the user, the list maythen include the new credit card account, which may be selected by theuser for provisioning to the mobile wallet. Again, the new credit cardaccount may be provisioned to the mobile wallet without any manual entryby the user of account information regarding the new credit card account(other than the selection of the new credit card account by the user,indicating that the user wishes to add the new credit card account tothe mobile wallet).

In the case of a new credit card account, the bank may issue a newcredit card account immediately upon learning of the lost or stolencredit card associated with the previous credit card account. Typically,the bank may then mail the user a new physical/plastic credit card. Uponreceiving the new physical credit card, the user may then activate thenew credit card, e.g., by calling a credit card activation phone numberprinted on a sticker that has been placed on the card.

In some embodiments, the user may be provided with the option ofactivating the new credit card account through the mobile wallet. Forexample, the bank may perform a first activation of the new credit cardaccount for purposes of transactions implemented via a mobile wallet.Such an activation may be performed via the mobile wallet itself (i.e.,the user does not need to take any action outside of the mobile walletto have the new credit card account activated). For example, the usermay be prompted with a message indicating that the credit card accounthas not yet been activated, and querying whether the user wishes to doso no (e.g., “Click ‘Yes’ to activate your new credit card for yourmobile wallet”). For security purposes, the first activation does notactivate the credit card for non-mobile wallet transactions involvinguse of the plastic credit card. Rather, the bank may also perform asecond activation of the new credit card account for purposes oftransactions implemented via a physical credit card associated with thenew credit card account. Hence, the plastic credit card is not useablefor credit card transactions until the second activation occurs. Such anarrangement ensures that the user is in possession of the physicalcredit card before the physical credit card is activated for purposes oftransactions implemented via the physical credit card (e.g., acard-present transaction at a bricks and mortar merchant).

As will be appreciated, it may often take several days or more for a newphysical credit card to be produced and delivered to the user after theuser reports a previous credit card as having been lost or stolen. Inthe arrangement described herein, the credit card account may beactivated for mobile wallet transactions much earlier, before the creditcard is activated for the non-mobile wallet transactions involving useof the plastic credit card. For example, the credit card account may beactivated one or more days before the user receives the plastic creditcard, or even within one day of the bank receiving the report from theuser that the plastic credit card has been lost or stolen. In someembodiments, the new credit card account may be activated for the mobilewallet within one hour or less of receiving the report from the userthat the plastic credit card has been lost or stolen.

In other embodiments, when a credit card is reported as lost or stolen,the mobile wallet computer system 120 may permit the user to continueusing the credit card number associated with the plastic credit card formobile wallet transactions, but prevent the plastic credit card frombeing used for card-based transactions. When a physical credit card islost or stolen, the physical credit card has been compromised. However,for purposes of the mobile wallet bank computer system 120, the accountnumber is simply an account identifier. So long as the mobile wallet hasnot been compromised, the mobile wallet computer system 120 can ensurethe integrity of the transaction based on the fact that the user is inpossession of the mobile device 110, particularly in situations where ata point of sale a tokenized card number is used, anyway (e.g., asdescribed above in connection with FIG. 2 ).

Referring now to FIG. 4 and FIGS. 4A-4D, FIG. 4 is a flow chart of aprocess 400 detailing a payment code generation process for anauthenticated mobile wallet session, according to an example embodiment.FIGS. 4A-4D are screens that may be displayed to the user during theprocess 400 of FIG. 4 according to an example embodiment. Process 400may be executed for a user requesting to execute a payment (e.g.,transaction) with a merchant or other recipient 140. Process 400 may beexecuted by a mobile wallet bank computer system 120 configured tomanage the user mobile wallet account.

FIG. 4A shows a mobile banking screen that may be displayed to the userafter the mobile wallet application has been installed on the mobiledevice 110. Similar to FIG. 3B, the user is prompted in FIG. 4A toprovide full online banking login credentials (fields 323 and 325). Byproviding such credentials in fields 323 and 325, the user may beprovided with the full functionality of the online banking website.However, in FIG. 4A, the user is also provided with a second option,namely to provide mobile wallet login credentials (via selecting button425). Hence, in FIG. 4A, the user is presented with two possibleauthentication paths, a first authentication path that prompts the userto provide online banking login credentials to gain access to onlinebanking, and a second authentication path that prompts the user toprovide mobile wallet login credentials to gain access to the mobilewallet. If the user selects the second authentication path, the user isdelivered to the more payment-focused functionality of the mobilewallet.

Process 400 includes receiving a PIN from the user (step 402) toauthenticate the user (FIG. 4B). At step 402 the mobile wallet clientapplication 116 prompts the user for a PIN that was used during theregistration steps in process 300. Hence, as previously indicated, theuser may be authenticated based on the user's mobile wallet bankingcredentials (e.g., 4 digit PIN), rather than being prompted to providethe user's usual online banking authentication credentials (username andpassword).

In an alternative embodiment, a user may log into a mobile bankingsession with a source account bank computer system, or the user maydirectly access the mobile wallet bank computer system. Process 400further includes allowing the user access to his or her mobile walletaccount (step 404). For example, the user may access his or her mobilewallet account through his or her account at the source account bankcomputer system, or may log into his or her mobile wallet account at themobile wallet bank computer system by providing a PIN or otheridentifier to the mobile wallet bank computer system.

Process 400 further includes validating the user based on the customertoken and device token (step 406). When the user logs in to access hisor her mobile wallet account, the customer token and device token storedon the mobile device (stored during step 310 of process 300) areprovided to the mobile wallet bank computer system. The mobile walletbank computer system validates the user and/or the mobile device for usewith the mobile wallet account. Step 406 may further include validatingthe user based on the PIN or other identifier also provided to themobile wallet bank computer system. For example, in order to bevalidated, the customer token, the device token, and the PIN may allneed to match (i.e., be associated with each other in the mobile walletcomputer system 120). As previously indicated, each user may have onecustomer token and one PIN which together are associated with multipledevice tokens (such that the user can access the mobile wallet accountfrom multiple devices).

Process 400 further includes generating a new device token (step 408),and sending the new device token to the mobile device of the user (step410). Hence, in some embodiments, the device token may change each timethe user uses the device. The device token may be a token that willidentify the user and the associated mobile device to the mobile walletbank computer system in the future. More particularly, the device tokenmay identify a current session of the user. In other words, the tokenmay be used to identify a particular function that the user may performduring the session, such as initiating a purchase. The token isencrypted by the mobile wallet bank computer system and provided to themobile device. The mobile device stores the device token for future use.

Process 400 further includes receiving an indication that the userwishes to execute a payment or other transaction (step 412). Upon theindication, the mobile wallet bank computer system generates a code(e.g., a QR code) based on the user's default payment method (step 414)(FIG. 4C). The QR code is generated including a combination of randomdigits and account information of the user. For example, the QR code mayinclude the last four digits of a debit card or credit card number of anaccount associated with the user and the request. The accountinformation may be used to identify a source account for the transactionat a later step in the transaction. The mobile wallet bank computersystem 120 may use token information (e.g., customer token and devicetoken information) from the mobile device to identify the mobile walletaccount and associated source account to use in code generation. Thecode may provide credit card data or tokenized credit card data in Track1 or Track 2 format, as described below with reference to FIGS. 5-7 .The generated code is then provided as part of a payment token to themobile device and/or to the merchant or other recipient of the paymentor funds (step 416) (FIG. 4D).

Referring to FIGS. 5-6 , codes that may be sent during operation of thesystem 100 are shown. As previously indicated, information embedded inthe codes may be embedded in a Track 1 format and Track 2. The code maybe sent optically as a code or in another manner. As will beappreciated, the code formats shown in FIGS. 5-6 are example codeformats that may be used with the systems and methods described herein.In other embodiments, other formats may be used.

The Track 1 format in FIG. 5 is shown to include 76 digits and the Track2 format in FIG. 6 is shown to include 38 digits. Each format maygenerally include a format code (digit 1), tokenized primary accountnumber 501 (digits 2-20), a field separator (digit 21), an expirationdate 505 (digits 35-38 in Track 1, digits 22-25 in Track 2), a servicecode (digits 39-41 or 26-28), and a payment token 507 (digits 42-76 or29-38). Each track may additionally or alternatively include otherfields representing different data to be embedded in the code. In oneembodiment (the Track 1 format), the credit card data may include acustomer name or other customer identifier (e.g., in digits 22-33 of theTrack 1 format).

In various embodiments of the present disclosure, account informationassociated with the user's mobile wallet account may be represented inthe code using digits 2 through 20 of the Track 1 or Track 2 format.This is shown in FIGS. 5-6 as the tokenized primary account number(TPAN). Referring also to FIG. 8 , the TPAN format is shown in greaterdetail.

As shown in FIG. 7 , the first six digits of the TPAN may represent anissuer identification number (IIN) that is used to route the TPAN to theappropriate mobile wallet bank computer system 120. The IIN is apredetermined number issued to each bank for financial institution forrouting fund transfer requests. In the present configuration, an TINthat is associated with the bank that operates the mobile walletcomputer system 120 may be used.

Digits 7 through 15 of the TPAN may represent a Trace ID, and digits 16through 19 may represent account information (e.g., the last four digitsof an actual account number, or other account information). Firstgenerating random numbers for digits 7 through 14 may create the TraceID. The Trace ID may be used for verifying and approving a userinitiated transaction. Once those digits are determined, then digit 15may be calculated. Digit 15 is calculated such that digit 19 may be usedas the checksum digit of the tokenized card number or the code. In otherwords, even though digit 19 is fixed (as part of the actual card numberof the account), digit 19 may be used as the checksum digit, becausedigit 15 is calculated in such a way to allow the code to pass the errordetection process. Digits 1-19 from FIG. 7 map to digits 2-20 in FIGS. 5and 6 . For example, digits 2-20 of FIGS. 5 and 6 may include the IIN,Trace ID, pseudo check digit, last 4 digits of the card number as shownin FIG. 7 .

The checksum digit is used for error detection purposes (e.g., to detecterrors in manually inputted data that is included in the code). Forexample, the checksum digit is used to help detect single digit errors,errors where digits are transposed, twin errors, etc. The checksum digitmay then be used in one of several algorithms for checking for errors inthe code. It should be appreciated that one of any type of checksumalgorithm may be used with the embodiment described herein.

In other embodiments, a digit other than digit 15 may be used as thecalculated digit. For example, any eight of the nine digits betweendigit 7 and 15 may be randomized, and the remaining digit may be used asthe “checksum helper” digit (e.g., the digit calculated to make digit 19the checksum digit).

Referring also to FIG. 8 , actual card number is sent in Track 2 formatthat may be generated at step 810 is shown in greater detail. Ascompared to the QR code of FIGS. 5-7 , the trace ID is moved to digits26-33, and the actual account number may be provided as digits 2 through17. In other words, a subset of the original token generated by themobile wallet bank computer system is moved into a discretionary fieldof the new generated token. The code is shown to generally include thetrace ID and account number, along with an expiration date field (e.g.,with the same digits as determined in an earlier process of creating theoriginal token) and a service code field. The code may optionallyinclude any other type of information.

In various embodiments, using the trace ID may allow the financialinstitution to identify mobile wallet transactions. Upon identifying themobile wallet transactions, the financial institution may segment themobile wallet transactions for risk, customer service, security, andcard not present transactions. In other embodiments, the transactionsthat were performed using mobile wallet bank computer system 120 eachuse a trace identification number and the user may be charged adifferent fee for such transactions. In various embodiments, when a userof a mobile wallet account loses their credit card or debit card and thefinancial institution issues the user a new credit card or debit card,the mobile wallet may be able to auto provision the newly issued cards.Auto provisioning may allow the user to use the mobile wallet accountprior to receiving and/or activating the credit or debit card. In otherembodiments, in the case of mobile wallet fraud, the mobile walletaccount of the user may be reset.

A credit card may be used to pay for a transaction at a point of salelocation using the physical credit card, known as a credit card presenttransaction. A credit card may be used when a credit card is notphysically located at a merchant location, such as but not limited to,an online merchant transaction where the credit card information isentered in an online transaction. A financial institution may rank therisk of fraud for each type of transaction. In some embodiments, thefinancial institution may assign a higher risk rating to a credit cardthat is not present at the merchant location than a credit card presenttransaction. In various embodiments, a mobile wallet that performs atransaction at a merchant location may be considered more secure than aphysical credit card because the mobile wallet does not provide themerchant the actual credit card number and the mobile wallet does nothave the actual credit card number. Accordingly, the financialinstitution may determine that a transaction was a mobile wallettransaction based on the trace ID and rate the transaction to be moresecure or fraud resistant than card present transaction. The financialinstitution may create a new risk rating that is of a lower risk formobile wallet transactions. In some embodiments, the transactions thatare performed using a mobile wallet may be charged different fee becauseof the risk rating. In various embodiments, due to the reduction of riskthe mobile wallet transactions may be charged a lower fee than cardpresent or card not present transactions.

FIG. 9 illustrates a process 900 that may be implemented by the systemin FIG. 1 . In various embodiments, process 900 may be used when anaccount holder reports their physical card lost or stolen via telephone,Internet, mobile device, etc. In some embodiments, process 900 may allowthe account holder to perform one or more transactions using the mobilewallet stored on a mobile device, even after the physical card has beenlost or stolen. Some advantages of process 900 may include the accountretaining the use of the account even after the loss of a physical card.Additional advantages may include the account holder being able toactivate the newly issued replacement card by using the mobile walletfunctionality.

At step 903, the financial institution computer system may receive amessage from the user that the physical card is lost or stolen. Invarious embodiments, the account holder may contact the financialinstitution computer system using various communication methods, such asbut not limited to, telephone, Internet, and mobile device. Uponreceiving the message from the account holder that the physical card islost or stolen, the financial institution computer system may ask theaccount holder whether the mobile wallet account has also beencompromised. After receiving input from the account holder that themobile wallet account holder has not been compromised, the financialinstitution computer system may deactivate the physical card account, atstep 905. In some embodiments, the financial institution computer systemmay assign the uncompromised mobile wallet account to a temporaryaccount to allow the account holder to conduct transactions using themobile wallet.

In various embodiments, the financial institution computer system mayreceive a request for a transaction from a merchant, at step 907. Atstep 909, the financial institution computer system determines whetherthe transaction is being performed by a mobile wallet or whether thetransaction is being performed by the physical card information. Sincethe mobile wallet transaction is performed using at least a trace ID,the financial institution computer system may differentiate between themobile wallet transaction and the physical card information transaction.

Upon determining that the transaction request is not from a mobilewallet or is using the actual card information, the financialinstitution computer system may deny the transaction request, at step911. The financial institution computer system would be able to avoidany fraudulent transactions using the actual card information by denyingthe transaction request that did not originate from a mobile walletassociated with the account.

When the financial institution computer system determines that thetransaction request originated from a mobile wallet account, thefinancial institution may determine whether a new replacement cardnumber has been issued to the account holder at step 913. If a newreplacement card number has not been issued, the financial institutionmay approve the transaction at step 915 based on the determination thatthe transaction is a mobile wallet transaction and based on the factthat the mobile wallet account has not been compromised. In someembodiments, the transaction may be approved using the temporary cardnumber discussed above.

In various embodiments, when the financial institution has issued a newcard, but account holder has not activated the physical card because theaccount holder has not received the card or other reasons, the financialinstitution may update its records with respect to the mobile wallet.For example, at step 917, the financial institution computer system mayupdate its records to associate the new card number with the mobilewallet account of the previous card number at step 917. After step 917,the financial institution may send an approval for the transactionrequest at step 919. In other embodiments, the mobile wallet clientapplication on the mobile device 110 may prompt the user to activate thecard prior to the user having received the physical card. In otherembodiments, even after receiving the card the account holder may wishto activate the card via the mobile wallet application. Activating thecard by the account holder, may update the financial institutionsettings to associate the new card number with the mobile wallet accountnumber.

FIG. 10 illustrates a payment process that may be implemented by thesystem in FIG. 1 according to an example embodiment. Except as otherwisedescribed below, the payment process of FIG. 10 is the same as thepayment process of FIG. 2 . Hence, the above discussion with respect toFIG. 2 applies to FIG. 10 as well, except as otherwise described below.

In the embodiment of FIG. 10 , rather than providing the substitute cardnumber to the mobile wallet computer system 120 (as in FIG. 2 ), theacquirer processor computer system 145 provides the substitute cardnumber to a card network computer system 152. Hence, a tokenized cardnumber may be generated and ultimately delivered to the acquirerprocessor computer system 145 at steps 1001, 1003, 1005, 1007 in themanner described above in connection with steps 201, 203, 205, 207.

Next, at step 1009, the acquirer processor computer system 145 sends thetokenized card number to the card network computer system 152. Next, atstep 1011, the card network computer system 152 sends the tokenized cardnumber to the mobile wallet bank computer system 120. After receivingthe request from the card network computer system 152, the mobile walletbank computer system 120 may determine the actual card number and sendthe actual card number back to the acquirer processor at step 1012. Inone embodiment, the determination of the actual card number may occur bysearching for the account information associated with the payment tokenand/or trace ID within the tokenized card number. Additionally, thetrace ID from the tokenized card number may be sent with the actual cardnumber at step 1012, similar to step 211. Again, at this point, theissuer discretionary field is no longer needed for the payment token,hence, the trace ID may be sent to the acquirer processor computersystem 145 in the issuer discretionary field.

At step 1013, the card network computer system 152 sends the actual cardnumber and the trace ID to the source account computer system 130 forprocessing a payment. The source account bank computer 130 may retrievethe trace ID that was received from the mobile wallet bank computersystem 120 by searching for the actual card number that was receivedfrom the payment system 150. The source account bank computer 130 maycompare the trace ID that was received/stored at step 1003 with thetrace ID that was received from the payment system 150 at step 1013.Assuming there is a match, the source account bank computer 130 mayissue an approval for the transaction. After verifying the actual cardnumber and the trace ID in the issuer discretionary field, the sourceaccount bank computer system 130 may send an approval to the paymentsystem 150 at step 1015. Steps 1017, 1019, and 1021 may be performed inthe same manner as discussed above in connection with steps 217, 219,and 221.

As discussed above in connection with FIG. 2 , the use of the paymenttoken and trace ID as described herein allows for two levels ofauthentication. The payment token is generated by the mobile walletcomputer system at step 1002. The payment token is then transmitted tothe mobile device 110, then to the merchant computer system 140, then tothe acquirer processor computer system 145, then to the card networkcomputer system 152, and eventually back to the mobile wallet computersystem 120 where it is matched with the original payment token generatedat step 1002. Similarly, the Trace ID is also generated by the mobilewallet computer system at step 1002, and then transmitted to the mobiledevice 110, then to the merchant computer system 140, then to theacquirer processor computer system 145, then to the card networkcomputer system 152, and eventually back to the mobile wallet computersystem 120 where it is matched with the Trace ID generated at step 1002.In the case of the Trace ID, however, the Trace ID is then furthertransmitted back to the payment system 150, and then to the sourceaccount computer system 130 where it is matched with the Trace IDgenerated at step 1002. Accordingly, the trace ID used in conjunctionwith the tokenized credit card number allows both the mobile wallet bankcomputer system 140 and the source account bank computer system 130 toauthenticate the transaction. Using the trace ID in the above describedmanner may permit the source account bank computer system 130 and themobile wallet bank computer system 120 to verify the trace ID at leasttwice prior to approving a transaction and transferring funds. Further,as previously discussed, the trace ID may be used by the source accountcomputer system 130 to determine whether the credit card transaction wasa mobile wallet transaction (e.g., as opposed to an in-personcard-present transaction involving use of the user's physical creditcard, as opposed to an online transaction, and so on). In otherembodiments, the mobile wallet computer system 120 generates a tokenizedcard number, but does not embed a trace ID in the tokenized card number.

In some embodiments, instead of embedding the trace ID in a tokenizedcredit card account number at step 1002, the actual credit card numberis transmitted to the mobile device 110 and the merchant computer system140. In such an embodiment, the trace ID may be included in the issuerdiscretionary field at step 1002, and the payment token may becommunicated in another manner or another payment matching mechanism maybe used. The trace ID may be stored in the issuer discretionary fieldand may travel though the payment processing system, until it isverified by the source account bank computer system 130. After beingverified by the source account bank computer system 130, the transactionmay be approved and the funds may be transferred from the source accountbank computer system to the acquirer processor computer system 145. Inother embodiments, the same financial institution may own the sourceaccount bank computer system 130 and the mobile wallet bank computersystem 120. Hence, as previously described in connection with thediscussion of FIG. 2 , the tokenized card account number and trace IDfeatures may each be used alone or in combination with each other.

The present disclosure contemplates methods, systems and programproducts on any machine-readable media for accomplishing variousoperations. The embodiments of the present disclosure may be implementedusing existing computer processors, or by a special purpose computerprocessor for an appropriate system, incorporated for this or anotherpurpose, or by a hardwired system. Embodiments within the scope of thepresent disclosure include program products comprising machine-readablemedia for carrying or having machine-executable instructions or datastructures stored thereon. Such machine-readable media can be anyavailable media that can be accessed by a general purpose or specialpurpose computer or other machine with a processor. By way of example,such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROMor other optical disk storage, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to carry or storedesired program code in the form of machine-executable instructions ordata structures and which can be accessed by a general purpose orspecial purpose computer or other machine with a processor. Combinationsof the above are also included within the scope of machine-readablemedia. Machine-executable instructions include, for example,instructions and data which cause a general purpose computer, specialpurpose computer, or special purpose processing machines to perform acertain function or group of functions. Software implementations couldbe accomplished with standard programming techniques with rule basedlogic and other logic to accomplish the various connection steps,processing steps, comparison steps and decision steps.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of what may beclaimed, but rather as descriptions of features specific to particularimplementations. Certain features described in this specification in thecontext of separate implementations can also be implemented incombination in a single implementation. Conversely, various featuresdescribed in the context of a single implementation can also beimplemented in multiple implementations separately or in any suitablesubcombination. Moreover, although features may be described above asacting in certain combinations and even initially claimed as such, oneor more features from a claimed combination can in some cases be excisedfrom the combination, and the claimed combination may be directed to asubcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the implementations described above should not beunderstood as requiring such separation in all implementations, and itshould be understood that the described program components and systemscan generally be integrated in a single software product or packagedinto multiple software products embodied on tangible media.

Thus, particular implementations of the subject matter have beendescribed. Other implementations are within the scope of the followingclaims. In some cases, the actions recited in the claims can beperformed in a different order and still achieve desirable results. Inaddition, the processes depicted in the accompanying figures do notnecessarily require the particular order shown, or sequential order, toachieve desirable results. In certain implementations, multitasking andparallel processing may be advantageous.

The claims should not be read as limited to the described order orelements unless stated to that effect. It should be understood thatvarious changes in form and detail may be made by one of ordinary skillin the art without departing from the spirit and scope of the appendedclaims. All implementations that come within the spirit and scope of thefollowing claims and equivalents thereto are claimed.

What is claimed is:
 1. A computer-implemented method, comprising:presenting, by a mobile device, a first user interface of a mobilebanking application on a display device of the mobile device to a user;providing, by the mobile device, an option to a create a mobile walletfrom the first user interface; receiving, by the mobile device, aselection of the option to create the mobile wallet on the mobiledevice; installing, by the mobile device, a mobile wallet application onthe mobile device based on receiving the selection of the option tocreate the mobile wallet on the mobile device; providing, by the mobiledevice, a second user interface of the mobile banking application thatincludes a mobile wallet icon on the display device of the mobiledevice; receiving, by the mobile device, a selection of the mobilewallet icon to provide access to the mobile wallet application;accessing, by the mobile device during a first mobile wallet sessionbased on the selection of the mobile wallet icon, a list of accountsheld by the user; providing and displaying, by the mobile device duringthe first mobile wallet session, the list of accounts held by the userfrom within the mobile wallet application; receiving, by the mobiledevice during the first mobile wallet session, a first device tokenidentifying the mobile device and the first mobile wallet session;receiving, by the mobile device, a selection of at least one accountfrom the list of accounts to provision to the mobile wallet application,wherein the at least one account from the list of accounts isprovisioned automatically to the mobile wallet application withoutmanual entry of an account number associated with the at least oneaccount; providing, by the mobile device, the first device token toauthenticate a second mobile wallet session; receiving, by the mobiledevice during the second mobile wallet session, an updated list ofaccounts held by the user, the updated list of accounts excluding apreviously-provisioned account that is no longer available for use in amobile wallet transaction; receiving, by the mobile device during thesecond mobile wallet session, a second device token identifying themobile device and the second mobile wallet session, the second devicetoken replacing the first device token; providing, by the mobile device,the second device token to authenticate a third mobile wallet session;providing, by the mobile device during the third mobile wallet session,a notification to the user to activate a new account, wherein activatingthe new account activates the new account for mobile wallet transactionsprior to the user receiving a physical card associated with the newaccount; storing, by the mobile device, an offline code generated by amobile wallet bank computer system and transmitted to the mobile device,the offline code accessible to the mobile device during an offlinemobile wallet transaction; and providing, by the mobile device, theoffline code to a merchant during the offline mobile wallet transaction.2. The method of claim 1, wherein the list of accounts includes at leastone of a demand deposit account, a credit card account, and a savingsaccount.
 3. The method of claim 1, wherein the list of accounts includesa current account balance for at least one account in the list ofaccounts.
 4. The method of claim 3, further comprising: receiving, bythe mobile device, an updated current account balance each time atransaction occurs.
 5. The method of claim 1, further comprising:storing, by the mobile device, a second offline code generated by themobile wallet bank computer system and transmitted to the mobile device,the second offline code accessible to the mobile device during a secondoffline mobile wallet transaction.
 6. The method of claim 1, furthercomprising: providing, by the mobile device, a second updated list ofaccounts including an account newly activated by the user or an accountnewly deactivated by the user.
 7. A mobile device, comprising: a displaydevice; and a processor coupled to the display device and a computerreadable medium, the computer readable medium having instructions storedtherein that, when executed by the processor, cause the processor to:present, via the display device, a first user interface of a mobilebanking application of the mobile device to a user; provide, via thedisplay device, an option to a create a mobile wallet from the firstuser interface; receive a selection of the option to create the mobilewallet; install a mobile wallet application on the mobile device;provide, via the display device, a second user interface on the mobilebanking application that includes a mobile wallet icon on the displaydevice of the mobile device; receive a selection of the mobile walleticon; provide and display, via the display device during a first mobilewallet session, a list of accounts held by the user from within themobile wallet application; receive, during the first mobile walletsession, a first device token identifying the mobile device and thefirst mobile wallet session; receive a selection of at least one accountfrom the list of accounts; provision the at least one account to themobile wallet application, wherein the at least one account from thelist of accounts is provisioned automatically to the mobile walletwithout manual entry of an account number associated with the at leastone account; provide the first device token to authenticate a secondmobile wallet session; receive, during the second mobile wallet session,an updated list of accounts held by the user, the updated list ofaccounts excluding a previously-provisioned account that is no longeravailable for use in mobile wallet transactions; receive, during thesecond mobile wallet session, a second device token identifying themobile device and the second mobile wallet session, the second devicetoken replacing the first device token; provide the second device tokento authenticate a third mobile wallet session; provide, via the displaydevice during the third mobile wallet session, a notification to theuser to activate a new account, wherein activating the new accountactivates the new account for use in future mobile wallet transactionsprior to the user receiving a physical card associated with the newaccount; store an offline code generated by a mobile wallet bankcomputer system, the offline code accessible during an offline mobilewallet transaction; and provide the offline code to a merchant duringthe offline mobile wallet transaction.
 8. The mobile device of claim 7,wherein the instructions further cause the processor to: provide, viathe display device, a second updated list of accounts including anaccount newly activated by the user or an account newly deactivated bythe user.
 9. The mobile device of claim 7, the list of accountsincluding at least one of a demand deposit account, a credit cardaccount, and a savings account.
 10. The mobile device of claim 7,wherein the instructions further cause the processor to: provide, viathe display device, a current account balance for at least one accountin the list of accounts.
 11. A computer-implemented method, comprising:presenting, by a mobile device, a first user interface of a mobilebanking application by a display device of the mobile device to a user;providing, by the mobile device, an option to create a mobile walletfrom the first user interface; receiving, by the mobile device, aselection of the option to create the mobile wallet on the mobiledevice; installing, by the mobile device, a mobile wallet application onthe mobile device based on receiving the selection of the option tocreate the mobile wallet on the mobile device; providing, by the mobiledevice, a second user interface of the mobile banking application thatincludes a mobile wallet icon via the display device of the mobiledevice; receiving, by the mobile device, a selection of the mobilewallet icon to provide access to the mobile wallet application;accessing, by the mobile device during a first mobile wallet sessionbased on the selection of the mobile wallet icon, a list of accountsheld by the user; providing and displaying, by the mobile device duringthe first mobile wallet session, the list of accounts held by the userfrom within the mobile wallet application; receiving, by the mobiledevice during the first mobile wallet session, a first device tokenidentifying the mobile device and the first mobile wallet session;receiving, by the mobile device, a selection of at least one accountfrom the list of accounts to provision to the mobile wallet application,wherein the at least one account from the list of accounts isprovisioned automatically to the mobile wallet application without anymanual entry of an account number associated with the at least oneaccount; providing, by the mobile device, the first device token toauthenticate a second mobile wallet session; receiving, by the mobiledevice during the second mobile wallet session, an updated list ofaccounts held by the user, the updated list of accounts excluding apreviously-provisioned account that is no longer available for use in amobile wallet transaction; receiving, by the mobile device during thesecond mobile wallet session, a second device token identifying themobile device and the second mobile wallet session, the second devicetoken replacing the first device token; providing, by the mobile device,the second device token to authenticate a third mobile wallet session;providing, by the mobile device during the third mobile wallet session,a notification to the user to activate a new account, wherein activatingthe new account activates the new account for mobile wallet transactionsprior to the user receiving a physical card associated with the newaccount; and providing, by the mobile device, a second updated list ofaccounts including an account newly activated or an account newlydeactivated.
 12. The method of claim 11, the list of accounts includingat least one of a demand deposit account, a credit card account, and asavings account.
 13. The method of claim 11, further comprising:providing and displaying, by the mobile device, a current accountbalance for at least one account in the list of accounts.
 14. The methodof claim 13, further comprising: receiving, by the mobile device, anupdated current account balance each time a transaction occurs.
 15. Themethod of claim 11, further comprising: receiving, by the mobile device,an offline code for use in a future mobile wallet transaction;providing, by the mobile device, the offline code to a merchant in thefuture mobile wallet transaction.
 16. The method of claim 11, furthercomprising: storing, by the mobile device, an offline code generated bya mobile wallet bank computer system and transmitted to the mobiledevice, the offline code accessible to the mobile device during anoffline mobile wallet transaction; and providing, by the mobile device,the offline code to a merchant during the offline mobile wallettransaction.